Ugh. I can easily add the beta annotation in kube-proxy, but the Ingress one is dicier after we've shipped, isn't it?

oh yeah, let me pull that commit out

On Thu, Dec 3, 2015 at 5:10 PM, Zach Loafman notifications@github.com
wrote:

Ugh. I can easily add the beta annotation in kube-proxy, but the Ingress
one is dicier after we've shipped, isn't it?

—
Reply to this email directly or view it on GitHub
#18187 (comment)
.

Ugh, now that it is out, I should roll it back in head, I guess.

On Thu, Dec 3, 2015 at 5:15 PM, Tim Hockin thockin@google.com wrote:

oh yeah, let me pull that commit out

On Thu, Dec 3, 2015 at 5:10 PM, Zach Loafman notifications@github.com
wrote:

Ugh. I can easily add the beta annotation in kube-proxy, but the Ingress
one is dicier after we've shipped, isn't it?

—
Reply to this email directly or view it on GitHub
#18187 (comment)
.

OK, this is 2 of the 3 commits in the original PR

I like it. LGTM.

Labelling this PR as size/S

GCE e2e build/test failed for commit 21c696f80928551e9016ba8cf31b3ceafc421e7f.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot test this

GCE e2e build/test failed for commit d42d874.

• Build Log
• Test Artifacts
• Internal Jenkins Results

GCE e2e build/test failed for commit d42d874.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot test this please

GCE e2e test build/test passed for commit d42d874.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@k8s-bot unit test this

Green! Merging.